Systems and methods for monitoring a primary operating system (OS) and/or migrating data using an OS hypervisor

ABSTRACT

Systems and methods for monitoring a primary Operating System (OS) and/or migrating data using an OS hypervisor. In some embodiments, an Information Handling System (IHS) includes a processor; and a memory coupled to the processor, the memory having program instructions stored thereon that, upon execution by the processor, cause the IHS to: provide an Operating System (OS) hypervisor configured to enable operation of a primary OS environment and a service OS environment concurrently, wherein the primary and service OS environments are distinct from each other; and allow the service OS, via the OS hypervisor, to monitor a state of the primary OS while forbidding the primary OS from monitoring a state of the service OS.

FIELD

This disclosure relates generally to computer systems, and morespecifically, to systems and methods for monitoring a primary OperatingSystem (OS) and/or migrating data using an OS hypervisor.

BACKGROUND

As the value and use of information continues to increase, individualsand businesses seek additional ways to process and store information.One option is an Information Handling System (IHS). An IHS generallyprocesses, compiles, stores, and/or communicates information or data forbusiness, personal, or other purposes. Because technology andinformation handling needs and requirements may vary between differentapplications, IHSs may also vary regarding what information is handled,how the information is handled, how much information is processed,stored, or communicated, and how quickly and efficiently the informationmay be processed, stored, or communicated. The variations in IHSs allowfor IHSs to be general or configured for a specific user or specific usesuch as financial transaction processing, airline reservations,enterprise data storage, global communications, etc. In addition, IHSsmay include a variety of hardware and software components that may beconfigured to process, store, and communicate information and mayinclude one or more computer systems, data storage systems, andnetworking systems.

In many situations, an IHS may need to be serviced or supported. Forexample, the IHS may have hardware and/or software that needs to befixed, updated, removed, installed, or replaced from time to time. Toaddress these, and other problems, certain systems and methods describedherein may enable a computer manufacturer or service provider to allowcustomers to have access to automated, simplified support actions oroperations, for example, even when an IHS is not otherwise able to bootto its primary or main Operating System (OS) or has other serioushardware or software failures.

SUMMARY

Embodiments of systems and methods for monitoring a primary OperatingSystem (OS) and/or migrating data using a hypervisor are describedherein. In an illustrative, non-limiting embodiment, an InformationHandling System (IHS) may include a processor; and a memory coupled tothe processor, the memory having program instructions stored thereonthat, upon execution by the processor, cause the IHS to: provide an OShypervisor configured to enable operation of a primary OS environmentand a service OS environment concurrently, wherein the primary andservice OS environments are distinct from each other; and allow theservice OS, via the OS hypervisor, to monitor a state of the primary OSwhile forbidding the primary OS from monitoring a state of the serviceOS.

In some implementations, the service OS may include one or morediagnostic tools. Monitoring the state of the primary OS may includeaccessing the state using an Application Programming Interface (API)provided by primary OS via the OS hypervisor to enable one-way access tothe primary OS by the service OS. The API may include a disk, file, ormemory access API, to name a few.

The program instructions upon execution by the processor, may furthercause the IHS to allow the service OS to suspend, stop, or restart theprimary OS via the OS hypervisor. Additionally or alternatively, theprogram instructions, upon execution by the processor, may further causethe IHS to: detect, by the OS hypervisor, that a primary OS event hastaken place; and notify the service OS, by the OS hypervisor, of theprimary OS event.

Additionally or alternatively, the program instructions, upon executionby the processor, may further cause the IHS to: determine, by theservice OS via the OS hypervisor, that the primary OS event meets athreshold; and take corrective action, by the service OS via the OShypervisor, upon the primary OS. Corrective action may include restoringa file affected by the primary OS event. Additionally or alternatively,corrective action may include a reboot of the primary OS.

The program instructions, upon execution by the processor, may furthercause the IHS to backup a partition where the service OS resides into aRandom Access Memory (RAM) prior to the determination. The partition mayinclude a solid-state portion of a hybrid Hard Disk Drive (HDD), andwherein the primary event may include an HDD failure. The programinstructions, upon execution by the processor, may further cause the IHSto restore the backup from the RAM to a replacement HDD in connectionwith a hot-swapping operation.

In another illustrative, non-limiting embodiment, a computer-implementedmethod may include providing an OS hypervisor configured to enableconcurrent execution of a primary OS and a service OS, where the primaryand service OS are distinct from each other; and allowing the serviceOS, using one or more one-way APIs provided via the OS hypervisor, tomonitor the primary OS while the primary OS is being executed.

In yet another illustrative, non-limiting embodiment, a storage devicemay have program instructions stored thereon that, upon execution by anIHS, cause the IHS to provide an OS hypervisor configured to enableconcurrent execution of a primary OS and a service OS, wherein theprimary and service OS are distinct from each other; and allow theservice OS, using one or more one-way APIs provided via the OShypervisor, to monitor the primary OS while the primary OS is beingexecuted.

In some embodiments, one or more of the techniques described herein maybe performed, at least in part, by an IHS operated by a user. In otherembodiments, these techniques may be performed by an IHS having aprocessor and a memory coupled to the processor, the memory includingprogram instructions stored thereon that, upon execution by theprocessor, cause the IHS to execute one or more operations. In yet otherembodiments, a non-transitory computer-readable medium or memory devicemay have program instructions stored thereon that, upon execution by anIHS, cause the IHS to execute one or more of the techniques describedherein.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention(s) is/are illustrated by way of example and is/arenot limited by the accompanying figures, in which like referencesindicate similar elements. Elements in the figures are illustrated forsimplicity and clarity, and have not necessarily been drawn to scale.

FIG. 1 is a diagram illustrating an example of an environment wheresystems and methods for providing service and support to computingdevices may be implemented according to some embodiments.

FIG. 2 is a block diagram of an example of an Information HandlingSystem (IHS) according to some embodiments.

FIG. 3 is a block diagram of an example of a service Basic I/O System(BIOS) according to some embodiments.

FIG. 4 is a flowchart of an example of a method for providing serviceand support in a computing device according to some embodiments.

FIG. 5 is a flowchart of an example of a method for providing backendservices and support to a computing device according to someembodiments.

FIG. 6 is a diagram of an example of system for an Operating System (OS)hypervisor according to some embodiments.

FIG. 7 is a flowchart of an example of a method for monitoring a primaryOperating System (OS) using an OS hypervisor according to someembodiments.

FIG. 8 is a flowchart of an example of a method for migrating data outof a hard disk partition into a Random Access Memory (RAM) according tosome embodiments.

FIG. 9 is a flowchart of an example of a method for migrating data froma RAM into a hard disk partition according to some embodiments.

DETAILED DESCRIPTION

To facilitate explanation of the various systems and methods discussedherein, the following description has been split into sections. Itshould be noted, however, that the various sections, headings, andsubheadings used herein are for organizational purposes only, and arenot meant to limit or otherwise modify the scope of the description orthe claims.

A. Overview

The inventors hereof have recognized a need for providing systems andmethods for service and support to computing devices. Existing toolsintended to facilitate service and/or support of a client device orInformation Handling System (IHS) do not adequately address numerousproblems, such as, for example, situations when the IHS fails to boot amain or primary Operating System (OS) for any reason, whether due to ahardware of software problem, such that the IHS is said to be in a“degraded state.” To address these and other concerns, embodimentsdescribed herein provide Basic I/O System (BIOS) and/or service OS-levelintelligence to enable a client device to self-diagnose and to receiveautomated service and support. Additionally or alternatively, in someembodiments, the main or primary OS may be modified to implement one ofmore of the foregoing features.

The term “degraded state,” as used herein, refers to the state of an IHSthat is not capable of booting a main or primary OS (e.g., WINDOWS®, MACOS®, LINUX®, etc.), either fully or partially (e.g., in WINDOWS®'s “safemode” or the like). When operating in a degraded state, the IHS maystill be able to execute BIOS instructions and/or a “service OS” (SOS).

The term “BIOS,” as used herein, refers to a type of firmware usedduring an IHS's booting process (e.g., power-on, or reset). The BIOSinitializes and tests an IHS' hardware components, and loads a bootloader or an OS from a memory device. The BIOS additionally provides anabstraction layer for the hardware which enables software executed bythe IHS to interact with certain I/O devices such as keyboards,displays, etc. Incidentally, the Unified Extensible Firmware Interface(UEFI) was designed as a successor to BIOS to address certain technicalissues. As a result, modern IHSs predominantly use UEFI firmware and theterm “BIOS,” as used herein, is intended also encompass UEFI firmwareand future variations thereof.

The term “service OS,” as used herein, refers to one or more programinstructions or scripts distinct from an IHS's “main OS” or “primary OS”such that, upon execution by an IHS (e.g., upon failure by the IHS toload the main or primary OS), enable one or more support, diagnostics,or remediation operations to be performed independently of the state ofthe main or primary OS. The service OS may include one or more serviceand support applications, as described in more detail below. In somecases, an SOS may be stored in a recovery partition of a hard drive.Additionally or alternatively, an SOS may be stored in a Non-VolatileMemory (NVM) or flash memory built into the client system. Additionallyor alternatively, the SOS may be stored in a remote location so as toallow an IHS to boot remotely “from the cloud.”

In some embodiments, service capabilities may be invoked either“pre-boot” or “pre-OS.” Pre-boot capabilities may be built into theBIOS/UEFI, and pre-OS capabilities may be provided by a service OS. Forexample, pre-boot services may include using enhanced BIOS diagnosticstools to detect hardware failure, providing a Quick Response (QR) codeto simplify access to support services, etc. Meanwhile, pre-OS servicesmay include enabling a service OS to provide customer automatedassistance, using built-in remediation scripts to help diagnose andremediate the device, improve support efficiency using live chat, remotecontrol support, etc. In some implementations, pre-boot services may befocused on “no-boot” scenarios, whereas pre-OS services may be focusedon operations such as remediation, boot from web, re-imaging from web,etc.

As will be understood by a person of ordinary skill in the art in lightof this disclosure, virtually any IHS environment that requires serviceor support may implement one or more aspects of the systems and methodsdescribed herein. Furthermore, certain aspects of the connected systemsdescribed herein may be implemented by computer manufacturers, softwareproviders, and/or service or support companies.

B. Service and Support Architecture

Turning now to FIG. 1, a diagram illustrating an example of anenvironment where systems and methods for providing service and supportto computing devices may be implemented is depicted according to someembodiments. As shown, each of any number of client devices 102A-N maybe an IHS or other computing device (generically referred to as “IHS102,” “client 102,” “client device 102,” or “device 102”) including, forexample, desktops, laptops, tablets, smartphones, and any otherall-in-one (AIO) data processing device. In some situations, devices 102may be located in geographically distributed or remote locations, suchas offices, homes, etc. Each device 102 may be operated by an individualend-consumer (e.g., lay person) or customer of a computer manufactureror software provider, for instance. In some cases, two or more of clientdevices 102A-N may be deployed within or managed by the sameorganization (e.g., a business).

Tools intended to facilitate service and/or support of client devices102 include service technicians 103, live support operators 104, and/orbackend service 105. Service technicians 103 include trained employeesor contractors that can travel to the site of device 102 or that canreceive the physical device 102 (e.g., at a retail store, by mail, etc.)or part(s) thereof in order to make repairs, for example. Live supportoperator(s) 104 may be available, for instance, when device 102 failsbut it is sufficiently operational that it can still connect the user tooperator(s) 104 via chat, email, text messages, Voice-Over-InternetProtocol (VoIP) call, etc. Additionally or alternatively, the user ofclient device 102 may place a conventional phone call to live supportoperator(s) 104 (e.g., using a 1-800 number or the like). In some cases,live support operator(s) 104 may interactively guide the user in aneffort to correct problems with client device 102 (e.g.,troubleshooting).

Backend service 105 may include one or more servers and/or IHSsconfigured to perform one or more automated operations with respect todevice 102. In various implementations, backend service 105 may beconfigured to communicate with a service OS prior to and/orindependently of IHS 102 being able to boot a main OS, and it may enableone or more support, diagnostics, or remediation operations to beperformed remotely including, but not limited to, telemetry, errorreporting, tracking, chat, etc.

Entities 102-105 may have access to network 101. In various embodiments,telecommunications network 101 may include one or more wirelessnetworks, circuit-switched networks, packet-switched networks, or anycombination thereof to enable communications between two or more ofIHSs. For example, network 101 may include a Public Switched TelephoneNetwork (PSTN), one or more cellular networks (e.g., third generation(3G), fourth generation (4G), or Long Term Evolution (LTE) wirelessnetworks), satellite networks, computer or data networks (e.g., wirelessnetworks, Wide Area Networks (WANs), metropolitan area networks (MANs),Local Area Networks (LANs), Virtual Private Networks (VPN), theInternet, etc.), or the like.

For purposes of this disclosure, an IHS may include any instrumentalityor aggregate of instrumentalities operable to compute, calculate,determine, classify, process, transmit, receive, retrieve, originate,switch, store, display, communicate, manifest, detect, record,reproduce, handle, or utilize any form of information, intelligence, ordata for business, scientific, control, or other purposes. For example,an IHS may be a personal computer (e.g., desktop or laptop), tabletcomputer, mobile device (e.g., Personal Digital Assistant (PDA) or smartphone), server (e.g., blade server or rack server), a network storagedevice, or any other suitable device and may vary in size, shape,performance, functionality, and price. An IHS may include Random AccessMemory (RAM), one or more processing resources such as a CentralProcessing Unit (CPU) or hardware or software control logic, Read-OnlyMemory (ROM), and/or other types of NVMs.

Additional components of an IHS may include one or more disk drives, oneor more network ports for communicating with external devices as well asvarious I/O devices, such as a keyboard, a mouse, touchscreen, and/or avideo display. An IHS may also include one or more buses operable totransmit communications between the various hardware components.

FIG. 2 is a block diagram of an example of an IHS. In some embodiments,IHS 200 may be used to implement any of computer systems or devices102A-N and/or 105. As shown, IHS 200 includes one or more CPUs 201. Invarious embodiments, IHS 200 may be a single-processor system includingone CPU 201, or a multi-processor system including two or more CPUs 201(e.g., two, four, eight, or any other suitable number). CPU(s) 201 mayinclude any processor capable of executing program instructions. Forexample, in various embodiments, CPU(s) 201 may be general-purpose orembedded processors implementing any of a variety of Instruction SetArchitectures (ISAs), such as the x86, POWERPC®, ARM®, SPARC®, or MIPS®ISAs, or any other suitable ISA. In multi-processor systems, each ofCPU(s) 201 may commonly, but not necessarily, implement the same ISA.

CPU(s) 201 are coupled to northbridge controller or chipset 201 viafront-side bus 203. Northbridge controller 202 may be configured tocoordinate I/O traffic between CPU(s) 201 and other components. Forexample, in this particular implementation, northbridge controller 202is coupled to graphics device(s) 204 (e.g., one or more video cards oradaptors) via graphics bus 205 (e.g., an Accelerated Graphics Port orAGP bus, a Peripheral Component Interconnect or PCI bus, or the like).Northbridge controller 202 is also coupled to system memory 206 viamemory bus 207, and to hard disk drive (HDD) 218. Memory 206 may beconfigured to store program instructions and/or data accessible byCPU(s) 201. In various embodiments, memory 206 may be implemented usingany suitable memory technology, such as static RAM (SRAM), synchronousdynamic RAM (SDRAM), nonvolatile/Flash-type memory, or any other type ofmemory. Conversely, HDD 218 may include any magnetic, solid-state (SSD),or hybrid data storage device capable of storing an OS and otherapplications.

Northbridge controller 202 is coupled to southbridge controller orchipset 208 via internal bus 209. Generally speaking, southbridgecontroller 208 may be configured to handle various of IHS 200's I/Ooperations, and it may provide interfaces such as, for instance,Universal Serial Bus (USB), audio, serial, parallel, Ethernet, or thelike via port(s), pin(s), and/or adapter(s) 216 over bus 217. Forexample, southbridge controller 208 may be configured to allow data tobe exchanged between IHS 200 and other devices, such as other IHSsattached to a network (e.g., network 101). In various embodiments,southbridge controller 208 may support communication via wired orwireless general data networks, such as any suitable type of Ethernetnetwork, for example; via telecommunications/telephony networks such asanalog voice networks or digital fiber communications networks; viastorage area networks such as Fiber Channel SANs; or via any othersuitable type of network and/or protocol.

Southbridge controller 208 may also enable connection to one or morekeyboards, keypads, touch screens, scanning devices, voice or opticalrecognition devices, or any other devices suitable for entering orretrieving data. Multiple I/O devices may be present in IHS 200. In someembodiments, I/O devices may be separate from IHS 200 and may interactwith IHS 200 through a wired or wireless connection. As shown,southbridge controller 208 is further coupled to one or more PCI devices210 (e.g., modems, network cards, sound cards, or video cards) and toone or more SCSI controllers 214 via parallel bus 211.

Southbridge controller 208 is also coupled to BIOS/UEFI 212 and to SuperI/O Controller 213 via Low Pin Count (LPC) bus 215. BIOS/UEFI 212includes non-volatile memory having program instructions stored thereon.Those instructions may be usable by CPU(s) 201 to initialize and testother hardware components and/or to load an OS onto IHS 200. Super I/OController 213 combines interfaces for a variety of lower bandwidth orlow data rate devices. Those devices may include, for example, floppydisks, parallel ports, keyboard and mouse, temperature sensor and fanspeed monitoring/control, among others. In various implementations,southbridge controller 208 may be configured to allow data to beexchanged between BIOS/UEFI 212 and another IHS attached to network 101(e.g., a remote server or other source of technical service) using wiredor wireless capabilities of network adapter 216.

In some cases, IHS 200 may be configured to provide access to differenttypes of computer-accessible media separate from memory 206. Generallyspeaking, a computer-accessible medium may include any tangible,non-transitory storage media or memory media such as electronic,magnetic, or optical media—e.g., magnetic disk, a hard drive, aCD/DVD-ROM, a Flash memory, etc. coupled to IHS 200 via northbridgecontroller 202 and/or southbridge controller 208.

The terms “tangible” and “non-transitory,” as used herein, are intendedto describe a computer-readable storage medium (or “memory”) excludingpropagating electromagnetic signals; but are not intended to otherwiselimit the type of physical computer-readable storage device that isencompassed by the phrase computer-readable medium or memory. Forinstance, the terms “non-transitory computer readable medium” or“tangible memory” are intended to encompass types of storage devicesthat do not necessarily store information permanently, including, forexample, RAM. Program instructions and data stored on a tangiblecomputer-accessible storage medium in non-transitory form may afterwardsbe transmitted by transmission media or signals such as electrical,electromagnetic, or digital signals, which may be conveyed via acommunication medium such as a network and/or a wireless link.

A person of ordinary skill in the art will appreciate that IHS 200 ismerely illustrative and is not intended to limit the scope of thedisclosure described herein. In particular, any computer system and/ordevice may include any combination of hardware or software capable ofperforming certain operations described herein. In addition, theoperations performed by the illustrated components may, in someembodiments, be performed by fewer components or distributed acrossadditional components. Similarly, in other embodiments, the operationsof some of the illustrated components may not be performed and/or otheradditional operations may be available.

For example, in some implementations, northbridge controller 202 may becombined with southbridge controller 208, and/or be at least partiallyincorporated into CPU(s) 201. In other implementations, one or more ofthe devices or components shown in FIG. 2 may be absent, or one or moreother components may be added. Accordingly, systems and methodsdescribed herein may be implemented or executed with other IHSconfigurations.

As mentioned above, in various embodiments certain service capabilitiesmay be built, at least in part, into a client device 102's BIOS/UEFI212. In that regard, FIG. 3 shows block diagram of an example ofBIOS/UEFI 212. Particularly, BIOS/UEFI 212 includes NVM mailbox 301configured to store program instructions that, upon execution, provideand/or receive one or more service and support parameters or information302 to or from control logic 303 of CPU(s) 201 to implement one or moreservice and support applications described in detail below. In somecases NVM mailbox 301 may serve as a “mailbox” to track issues and otherinformation persistently. As noted above, however, at least a part ofthe aforementioned service capabilities may be provided via a service OSthat is stored at least in part within a designated a partition of HDD318, and/or on a remote IHS accessible to BIOS/UEFI 212 via network 101.

C. Service and Support Applications

In some embodiments, a variety of service and support applications maybe at least partially embedded into BIOS/UEFI 212 and/or NVM mailbox301, as described below.

i. Automated Hardware Client Device Service and Support

Systems and methods described herein may include a service and supportapplication configured to provide automated services. In someembodiments, client device BIOS level intelligence may be provided toexecute self-diagnosis and to assist in automated services. Servicecapabilities are built into client device BIOS diagnostics pre-boot,service OS on disk, or boot from cloud. Moreover, these capabilities maybe integrated with a services backend for automated client device errorreporting, tracking, chat, remediation, etc.

In some embodiments, an automated diagnostics procedure of an automatedservice and support application may include performing a BIOSdiagnostics to discriminate hardware from software issues (e.g., brokenHDD or corrupt OS). Then, BIOS/UEFI 212's NVM mailbox 301 may be used totrack issues persistently from BIOS, pre-OS, OS, and/or backend sources.

Upon detection of a failure, a determination may be made as to theseverity of that failure (e.g., whether the failure is severe, such asin a no-video situation, a no-network scenario, etc., or whether it is asimple failure, such as an OS problem), and remedial action(s) may thenbe taken by the automated service and support application as deemedappropriate. For example, if a network is not available, a QuickResponse (QR) code or audio may be used to provide diagnostic failureand device identification information. Conversely, if the network isavailable, the automated service and support application may activate a“phone home” capability upon detection of a failure, and it may boot theclient device to a service OS.

In that scenario, the client device may connect directly with a backendservice Application Programming Interface (API) to initiate a warrantycheck (e.g., via hardware service tag as hardware ID), generate aservice case, update debug data, initiate recovery or remediationoperations, etc. In some cases, the automated service and supportapplication may trigger an automatic dispatch of customer replaceableunits (CRUs), parts, or components within the client device.

At the “point of need,” which often coincides with the “point offailure,” the automated service and support application may make serviceoffers based on failure diagnoses. For example, such service offers mayinclude an out of warranty upsell, warranty upgrade, additional serviceoffers (e.g., HDD recovery for dead drive upsell), warranty carry incapability (e.g., report closest repair facilities for carry inservice), etc.

Moreover, with respect to recovery and remediation, the automatedservice and support application may provide remote control, remotescripting/diagnostics, live customer support, backup, re-imaging and OSre-install via local factory image or via web, and the like.

ii. No-Video Support

Systems and methods described herein may include a service and supportapplication configured to provide technical support in no-videosituations, which are otherwise difficult to troubleshoot. In manycases, when client device 102 is not capable of outputting a videosignal, users have no other option but to place a phone call to themanufacturer, because the device itself can provide no help.

To address this, and other concerns, a service and support applicationas described herein may include a audio-only support system, forexample, similar to an automated phone support system or InteractiveVoice Response (IVR), but that is local to client device 102 and capableof running in a pre-OS or pre-Boot environment. While a customer isinteracting with the service and support application, client device 102can run a diagnostics procedure. When appropriate, the service andsupport application may handoff the local automated audio support toonline voice support from the IHS manufacturer. If network 101 isunavailable, client device 102 may prompt the user to connect directlyto a nearby device distinct from client device 102 to perform one ormore of these operations.

In some embodiments, the service and support application may includepre-OS availability of audio-based troubleshooting, offline audiosupport concurrent with diagnostics, and/or merging or handover betweenoffline and online audio support. The service and support applicationmay also prompt the user to make peer-to-peer (P2P) connection to anearby device, readout codes for diagnosis/dispatch verification, and/orprompt the user to add or insert external storage to which to outputdiagnostic results.

iii. Mayday Beacon

Systems and methods described herein may include a service and supportapplication configured to provide an automated and authenticated maydaybeacon, with a cost-effective 1-to-1 support for verified client device102's failures.

When client device 102 experiences a fault or hang before its main OS ismade available, a wireless signal beacon (e.g., Bluetooth, Wi-Fi, etc.)may be sent (e.g., on a periodic basis) containing verification of thedevice credentials issued at the time of manufacture, details regardingthe fault and a direct link to the manufacturer's support, decision treelocation, and/or whether a premium account is linked. The beacon may beauthenticated directly to a support representative with all failureinformation logged and available. This technique may prevent erroneoussupport calls by verifying the user has actually experienced a failureand authenticating that the proper support level has been funded, whichpromotes a low cost, one-on-one support service.

In some embodiments, the service and support application may beconfigured to broadcast a distress signal with credentials to makeauthenticated jump to a support site provided by backend services 105from a secondary device or infrastructure. A certificate may be issuedfrom the manufacturer containing client device 102's platform, userinformation, and/or service level. Such a certificate and a landing pagefor service may be passed automatically while client device 102 is outof service. Also, the service may be rendered utilizing secondary deviceor infrastructure via authenticated and verified client device 102experiencing failure.

iv. Network-Based Recovery and Service

Systems and methods described herein may include a service and supportapplication configured to provide network (e.g., Internet) recovery andservice.

When client device 102 fails, it may “phone home” and boot, from backendservices 105, a service OS to provide automated service and support. Aservice and support application in BIOS/UEFI 212 may include, forexample, a boot loader, where to go (e.g., an IP address), bootingproper image for machine, and/or a service application. As such, theservice and support application may provide a smarter BIOS/UEFI 212,smart diagnostics in BIOS/UEFI 212, intelligent boot selection to localdrive or web, and IP-awareness, among other features.

In some implementations, the service OS may be supported on manyplatforms and on many versions of those platforms. For example, a singleplatform (e.g., having a model name or number) may be shipped from themanufacturer with different hardware configurations (e.g., differentCPUs, etc.), thus each combination of platform and version requiringthat different, specific drivers be built into or provided for in theservice OS.

In some embodiments, the service and support application may beconfigured to provide a Unified Extensible Firmware Interface (UEFI)BIOS module with smart diagnostics and IP support intelligently controlsboot to a service OS. Client device 102 connects to backend services 105to get proper and latest service OS for that particular device. Backendservice or server 105 may receive a client manifest, and it maydynamically serve a service OS kernel, drivers, and a serviceapplication to client device 102 for recovery and/or remediation.

v. Reducing Perception of Wait Times

Systems and methods described herein may include a service and supportapplication configured to improve customer experience while downloadinga recovery OS by reducing the perception of wait time.

When client device 102 has a malfunction, it can boot to an alternateOS. In some cases, the alternate OS is downloaded via network 101 beforeclient device 102 is able to boot. The download time is variable, oftennontrivial, and may negatively affect customer perception. To counterthis, the service and support application may estimate the download timeof the alternate OS and, based on an assessment of the delay, may “pullforward” one or more low-bandwidth activities and/or options that thecustomer may need or desire to do anyway (e.g., updating contactinformation), thus helping save customer time and reducing theperception of delay.

In some embodiments, the service and support application may beconfigured to prioritize lower-bandwidth tasks based on estimated OSload time. Prioritization of activities may be based, for example, upondata about malfunction. As such, the application may enable user inputor interaction while OS is downloading (e.g., updating contactinformation, describing the problem that happened before failure, etc.).The application may also submit a phone number for text alerts whenfailed client device 102 is ready, and it may start a local interactivedebug troubleshooting operation while the OS is being downloaded.

vi. Identity Continuity in Service of Failed System

Systems and methods described herein may include a service and supportapplication configured to provide identity continuity in the servicingof a failed client device 102.

When client device 102 fails and needs service, a user may need to enterservice credentials on a service web portal provided by backend serviceor server 105, whether accessing the portal directly or via a serviceOS. However, the user may not recall such infrequently-used credentialsat the point of need. By storing both a main OS's user credential hashand a service portal token, a service and support application canauthenticate the user, and then automatically submit the service portaltoken to log user into the service portal without manual entry ofcustomer credentials. This method may also be used to allow access tocustomers Wi-Fi profiles, and other type of data that needs protection.

In some embodiments, the service and support application may beconfigured to use a BIOS's “mailbox” to communicate one or more servicestoken(s) to enable a single-sign-on procedure, while protecting thetoken(s) with user credentials.

vii. Smart Diagnosis and Triage of Failures

Systems and methods described herein may include a service and supportapplication configured to perform smart diagnosis and triage of clientdevice failures.

In some cases, the application may provide an automated method ofhardware exoneration, identifying software versus hardware issues withtargeted debug. POST may be used to detect issues during power onsequence, then those results may be used for firmware-based diagnosticsfor next level of hardware diagnostics. Main OS, POST and firmware baseddiagnostic results may be stored on the client device's BIOS's NVM or“mailbox” as device health data. In case client device 102 is not ableto boot its main OS, a service OS may be started and uses health data toeither run even more extensive hardware diagnostics or to run softwarefault detection and remediation test. Cloud connection to client device102's manufacturer or backend service 105 may facilitate the download ofupdated tests, reporting of issues, and initiation of replacement partsdispatch.

In some embodiments, the service and support application may beconfigured to use a BIOS's NVM or “mailbox” to aggregate device healthdata. The application may use firmware and/or a service OS. Each stageof diagnostics may use information from previous diagnostics results totarget more detailed but specific subsequent tests.

viii. Smart Diagnosis Using Hosted Resources

Systems and methods described herein may include a service and supportapplication configured to perform smart diagnosis using hostedresources. When client device 102 cannot boot after repeated attempts,it may begin a process to perform self-evaluation and potentiallyself-repair operations. Because having all executable diagnostics andrepair modules present in the non-bootable system would be costly,operations may involve successively loading software modules from aremote support source 105. But, modules loaded through internet/wirelessnetworks 101 are likely slow to download, and therefore should bereduced or minimized to be tailored exactly as needed for a givenprocess.

To address these, and other problems, in some embodiments a service andsupport application may be configured to upload test results to backendservice 105, which automatically determines a subsequent module to bedownloaded based on client device data and/or historic analysis of otherclient devices. The application may provide a remote boot of diagnosticand repair software modules. Appropriate modules may be selected and/orminimized to the next diagnosis stage in order to facilitate transferover slow communications channels. A service may provide a reverse proxyfor a hosted module to be loaded so that client device 102 may boot froma single Uniform Resource Locator (URL) for each process.

ix. Adaptive Boot Order

Systems and methods described herein may include a service and supportapplication configured to intelligently alter a boot order to aid inautomated client device diagnosis and repair. When client device 102fails to completely boot, it does not move on to another component, asset in the boot order, if a previously attempted component remainsavailable for boot. Often the process gets stuck trying to boot andrepair the main OS indefinitely. The pre-set boot order remains staticand unaltered.

In some embodiments, by building intelligence into BIOS/UEFI 212 fordetermining a boot order for client device 102, a service and supportapplication may be configured to break out of a failing sequence andload alternative OSs and/or repair and diagnostic modules from variouslocal or remotely available resources selected by their availability,performance, or content. Depending upon the success of each stage,client device 102 may change the boot order again to try another source.A successful repair may lead back to booting the main OS as the primaryboot resource. An alternative or service OS may result as the finalstage if the main OS cannot be made bootable.

In some embodiments, the service and support application may beconfigured to dynamically change a boot order based upon conditions ofclient device 102. The application may also set client device 102 intemporary or “permanent” boot orders based upon the completion stage ofthe diagnosis and repair.

x. Exporting of Failure and Diagnostic Data

Systems and methods described herein may include a service and supportapplication configured to export failure and diagnostic data from amalfunctioning client device. Client device 102 may sometimesmalfunction such that it cannot provide output or accept input from auser. It may still function at a low level, however, in order to captureits own failure codes and run diagnostics. These codes and diagnosticresults are written to internal storage and are useful for systemremediation, but unfortunately remain captive on the malfunctioningclient device.

To address these, and other problems, a service and support applicationmay create an embedded capability that is triggered by a malfunction,identifies the failure/diagnostics data, and exports the data uponinsertion of an external storage device. The external device may then betaken to a functioning IHS or other client device, which can receive thedata for local analysis and/or upload it for analysis or recordkeeping.

In some embodiments, the service and support application may beconfigured to export the data to an external device having a markerfile. The marker file may be generated by an IHS manufacturer orsoftware provider, and identifies the external device as belonging to anauthorized service technician or other party. As such, a service modemay be provided for malfunction situations in which a user cannotinteract with or extract data from failed client device 102. Normalbehavior that occurs when inserting an external storage device may beoverridden in the service mode, and instead client device 102 may exportrelated failure/debug data to the external device. The service mode maybe independent of the main OS.

xi. Technician Access to Service Data

Systems and methods described herein may include a service and supportapplication configured to provide technician access to only servicesdata on an encrypted drive. For diagnosis and remediation, client device102 may use services data (e.g., system telemetry, failure anddiagnostics data, services history, etc.). If a system has OS volumeencryption (e.g., BitLocker) and fails over to a service OS, the serviceOS cannot typically access the services data due to encryption. That is,the latest and most valuable services data is trapped.

To address these, and other concerns, service and support applicationmay create a separate services data partition in local storage (e.g.,client device 102's own hard drive), also encrypted for consistency withuser intent. The key for the services data partition may be differentthan the key used for the remainder of the volume encryption, and may bestored by backend service 105 with user permission to allow servicetechnician 103 access in controlled support situations. As such,services data may be kept outside the inaccessible encrypted OSpartition while still protected.

In some embodiments, the service and support application may beconfigured to create a services data partition that is encrypteddifferently (e.g., different key and/or encryption algorithm) thanclient device 102's main OS volume for purposes of services access.Access to the separately encrypted data may be useful to servicesapplications and only visible to an authorized technician. Also, theapplication may provide the ability to pull encryption key from cloudand decrypt service data on device distinct from the client device, forexample, using technician credentials (e.g., when network 101 is notaccessible by client device 102).

xii. Protecting the Service OS Administrator's Password

Systems and methods described herein may include a service and supportapplication configured to protect the service OS administrator'spassword while allowing technician one-time execution with elevatedprivileges. An initial password for a service OS may be created using aOne-Time Password (OTP) technique and a seed stored on client device102's BIOS/UEFI 212's NVM mailbox 301. The seed and a hardware servicetag may be sent to backend services 105 to provide a mechanism forservice technician 103 or live support operator(s) 104 to run privilegedapplications in the service OS without using a master password. In someembodiments, application of OTP in a support scenario may enable highersecurity for remote management and debug operations. NVM mailbox 301 maybe used for storing initial seed at factory tied to the client hardwareservice tag. A service technician at failure time may generate a code torequest administrator permissions.

xiii. Automatic Stop and Boot to Service OS

Systems and methods described herein may include a service and supportapplication configured to provide automatic system stop and boot to aservice OS for forensics analysis. In some embodiments, detection ofsuspicious activity for secure systems may result in automated boot toservice OS with automated forensics lockdown and analysis outside thepotentially compromised main OS. The application may combine securityintrusion or behavior capabilities with a service OS to provide newforensics features. For example, detection of intrusion or malware inclient device 102 may initiate lock down mode boot to the service OS.The service OS then connects or phones home to backend services 105report a potential security incident, and initiates data forensicscollection. Client device 102 may maintain a lockdown mode at BIOS levelcontrolled by policy to maintain security of network 101 and data forforensic analysis.

xiv. Migrating Contents of an Internal Storage Partition

Systems and methods described herein may include a service and supportapplication configured to migrate contents of an internal storagepartition to a replacement storage device.

In some embodiments, data contained on a secondary partition of clientdevice 102's internal drive storage may be migrated from an old orexisting drive to a replacement or upgraded drive by storing it inDynamic RAM (DRAM) while the drive is hot-swapped. If DRAM capacity isinsufficient, overflow may be handled by external storage (e.g., USBdrive), for example. In another embodiment, a Solid State Drive (SSD)portion may instead be a secondary partition on a standard hard drive.As such, an application may migrate a specified drive partition intoDRAM, use external storage for data that exceeds the capacity of DRAM,and/or recognize and provisions replacement storage with contents ofdrive partition. These, and other techniques, are described in moredetail in “Section E” below.

xv. Using a Service OS Via a Hypervisor

Systems and methods described herein may include a service and supportapplication configured to increase the effectiveness of a service OS byutilizing a custom hypervisor.

A conventional service OS may be configured to run on client device 102only when the main OS is suspended. Such a conventional service OS maynot be able to effectively monitor real-time events in the main OS asthey occur. For example, a conventional service OS may only be able toexamine the state of the primary disk, data, etc. using residual datacollected by the main OS when the main OS was running. To address these,and other concerns, a service OS as described herein may run in ahypervisor (in a first tier next to the main OS, or in a second tier),and the hypervisor may allow the service OS full access to the resourcesof the primary OS. Accordingly, dynamic state of the primary OS may bemonitored either constantly or periodically and actions and reports mayoccur immediately (a “watchdog” OS).

In some embodiments, a hypervisor environment may provide a service OSof client device 102 with full access to the resources of the main OS(but not necessarily vice-versa, for example, to keep the service OSfrom being corrupted). The service OS may run as a peer of the primaryOS. The peer, service OS may be configured to monitor for process,memory, disk and other resources of the main OS, and may be allowed toalter them as required. These, and other techniques, are described inmore detail in “Section E” below.

D. Methods for Providing Client Device Service and/or Support

FIG. 4 is a flowchart of a method for providing service and support in acomputing device. In some embodiments, method 400 may be performed, atleast in part, by BIOS/UEFI 212 and/or CPU(s) 201 of client device 102,for example, when client device 102 is operating in degraded state(e.g., no video, hard drive fault, etc.).

At block 401, method 400 includes attempting to boot client device 102.For example, block 401 may be executed in response to a power-on orreset event. Block 402 determines whether a Power-On-Self-Test (POST)procedure has been successfully performed upon client device 102 byBIOS/UEFI 212. If so, then block 404 determines whether a main OS hasbeen successfully booted. In some cases, a successful boot of the mainOS may include a complete success; in other cases, however, a“successful” boot may include cases where the main OS is booted in safemode, or the like, with less than all of its functionality available toa user. If block 404 detects successful boot of the main OS, thencontrol of client device 102 is passed to the main OS at block 406, andthe method ends. In that case, support and/or service issues may behandled by the main OS.

Conversely, if the POST operation fails at block 402, service andsupport may be provided in a pre-boot environment at block 403. Examplesof service and support procedures available to client device 102 in sucha scenario include, but is not limited to, detecting networkavailability, use of QR codes or the like (with or without networkconnections), collection and transmission of telemetry data and/or eventlogs, alerts and indications of failures, and procedures for dealingwith no-video scenarios, as outlined above.

If the main OS fails to boot at block 404, block 405 then determineswhether a service OS can be booted. In some cases, the service OS may beinitiated from a memory local to the client device. For example, theservice OS may be stored in NVRAM or in a designated partition of HDD218. Alternatively, the service OS may be loaded from a backend service105 over network 101 (e.g., cloud boot). If the service OS is notcapable of being booted at block 405, then service and support may againbe provisioned within the pre-boot environment at block 403. Otherwise,service and support operations may be provided in a pre-OS environmentat block 407, before method 400 ends.

In various implementations, BIOS/UEFI 212 may be configured to use a“boot strike count” as part of a failure detection procedure. That is,the number of unsuccessful main OS and/or service OS boot attempts maybe kept by BIOS/UEFI 212, and that information may be used by one ormore of the aforementioned service and support operations in subsequentboot attempts.

As noted above, in some cases, service and support may be provided to acomputer device such as client device 102 by backend services 105 vianetwork 101. In that regard, FIG. 5 is a flowchart of a method forproviding backend services and support to a computing device. In someembodiments, method 500 may be performed, at least in part, by BIOS/UEFI212 and/or CPU(s) 201 of client device 102 in cooperation with backendservices 105, for example, when client device 102 is operating indegraded state (e.g., no video, hard drive fault, etc.), either inpre-boot environment 402 or pre-OS environment 407 of FIG. 4.

At block 501, method 500 includes determining whether access to network101 is available to client device 102. If not, then service and supportoperations may be provided as local remediation operations (e.g., QRcode services, etc.) at block 502. If there is network access, however,block 503 includes client device 102 “phoning home” to reach backendservices 105, which in turn may perform one or more checks. Examples ofsuch checks include, but are not limited to, warranty and serviceentitlement checks performed using the client device 102's service tagor other identifying information such as the customer account token.

At block 504, method 500 includes uploading client device telemetryand/or debug data to backend services 105. For example, the telemetryand/or debug data may be used by backend service 105 to iterativelyimprove diagnostics and fault isolation. Then, at block 505, method 500includes any number of remote remediation and service operationsperformed by backend services 105. Examples of such operations include,but are not limited to, auto dispatch for CRUs, point of need services(such as warranty upsells, warranty upgrades, service offers, etc.), andHDD recovery (with optional reporting of closest location, office, orstore available for carry-in service by the user). Other operations mayinclude remote control of one or more components of client device 102,chat support, backup, re-imaging, OS re-install via local factory imageor cloud, etc.

E. Monitoring a Primary OS and Migrating Data

When a main OS—which is the primary software environment for acomputer—fails to run properly or exhibits signs of unusual behavior, itmay need to be observed and/or inspected by diagnostic applications.These diagnostic applications may either run as part of the primary OS(e.g., if the primary OS is functional enough to support the applicationand trustworthy enough to inspect itself) or under an alternate,“service OS” that may be booted and run instead of the primary OS. Theservice OS can then examine the primary storage medium (e.g., an HDD,etc.) containing the software and data space of the primary OS. Theseconventional methods for detecting errors and issues in the primary OSrevolve around analyzing diagnostics and data after the failure hasoccurred. A service OS booting to resolve primary OS issues is left toexamine the state of the primary disk and data using residual datacollected by the primary OS when it was running, as well as the staticstate of information left on the primary storage medium.

In contrast with the foregoing, systems and methods described herein mayinclude a service and support application configured to monitor aprimary Operating System (OS) and/or migrate data using an OShypervisor.

In various embodiments, a service OS running under an OS hypervisor withpermissions and full access to the primary OS may be configured todynamically monitor the state of the primary OS and initiate actions andreports, interceptions or alterations to the primary OS immediately. Assuch, the service OS may act as a “watchdog OS” for the primary OS undercontrol of the OS hypervisor.

In some cases, the service OS may be executed as a “tier 1” applicationnext to the primary OS. Additionally or alternatively, the service OSmay be executed a “tier 2” application on top of the primary OS. Thelatter implementation may be useful, for example, in situations wherethe primary OS remains trustworthy and functional.

In an OS hypervisor environment, according to some embodiments, ratherthan providing full isolation of two OSs (primary and service), theservice OS may be provided one-way access through programmaticApplication Programming Interfaces (APIs) to the primary OS environment.One-way APIs supported by the primary OS may include, but are notlimited to, disk, file and memory access, Windows ManagementInstrumentation (WMI) and hardware access through drivers.

Also, APIs provided by additional primary OS services to enhance thefunctionality of the service OS may be accessed. Normally, such accessthrough APIs would only be granted to applications running on theprimary OS. In various embodiments, however, the service OS, whilerunning simultaneously or concurrently with the primary OS may becapable of accessing the primary OS as if it were an application runningon the primary OS; while remaining protected from being corrupted orbrought down by the primary OS via the OS hypervisor.

In various implementations, the service OS may exist independently ofthe primary OS. For example, the service OS may be capable ofsuspending, stopping or restarting the primary OS. If the primary OS isunable to operate properly and support system level and other servicesenabled by its APIs in a reliable and trustworthy manner, then theservice OS may still access the hardware and software environment andexamine or change the state of the primary OS by utilizing theinterfaces provided by the OS hypervisor.

Additionally, since the service OS may have full access to all systemstorage and data as well as the OS hypervisor environment and basehardware access, it may be enabled to migrate any portion of theenvironment—including part of or the entire operating environment—into adynamic memory that the OS hypervisor reserves for storage. Backup filesof the service OS and OS hypervisor environment, which are stored on anHDD, may be used to allow for replacement of the OS hypervisor andservice OS. Then, if non-volatile storage such as the HDD is replaced,the service OS can reimage itself using system backup files to recoverthe machine state. This technique be useful, for example, for rapidreplacement (e.g., hot swapping) of failed storage media if thepartition or files containing the service OS and hypervisor backup arestill viable.

In some cases, when the primary operating system backups are too largeto fit in system DRAM, the service OS may copy those backups into DRAMwith overflow enabled to an additional attached storage (e.g., such asUSB). In this case, the backups copied and restored may be a completeoperating environment of both OSs and the OS hypervisor.

FIG. 6 is a diagram of an example of system for an Operating System (OS)hypervisor according to some embodiments. In system 600, OS hypervisor602 sits on top of base hardware layer (e.g., IHS 200 of FIG. 2). Inoperation, OS hypervisor 602 is configured to host two or more OSsoperating concurrently. In other embodiments, three or more OSs may bemanaged by OS hypervisor 601 (e.g., two different service OS and aprimary OS, or two primary OSs and one service OS, for instance).

Although, conventionally, primary OS 603 and service OS 604 would becompletely isolated from each other, here element 605 represents afirewall provided by an OS hypervisor API. In some embodiments, one-wayAPIs enabled in or through the OS hypervisor provide access to primaryOS 603 by service OS 604, but not vice-versa. Again, only APIs providedby the OS hypervisor allow the service OS 604 to access either the basehardware or primary OS 603. And because no APIs exist that are callablein the opposite direction (that is, from the primary OS toward theservice OS), service OS 604 remains protected against primary OS 603.

In addition, OS hypervisor 602 provides a set of one or more APIs fromprimary OS 603 to service OS 604. Through the API(s), service OS 604 iscapable of monitoring a state of primary OS 603. Again, examples ofthese API(s) include, but are not limited to, disk, file and memoryaccess, Windows Management Instrumentation (WMI), and hardware accessthrough drivers. For example, using such an API, service OS 604 mayaccess primary OS 603 to kill a process, direct read/write to modifyaffected disk bytes, uninstall software, or perform any other operationthat primary OS 603 is capable of performing upon itself.

And again, using OS hypervisor 602, service OS 604 is be capable ofaccessing the primary OS as if it were an application running on theprimary OS, but it cannot be corrupted by the primary OS. That is, OShypervisor 602 provides unidirectional, one-way access to primary OS 603by service OS 604.

FIG. 7 is a flowchart of an example of a method for monitoring a primaryOS using an OS hypervisor according to some embodiments. At block 701,OS hypervisor 701 starts. Then, at blocks 702 and 703, a primary OS anda service OS are booted or start, respectively. In some cases, the twoOSs may be started in any order and/or concurrently. At block 704, theprimary OS is put into normal operation by a user. At block 705, asoftware or hardware failure alters or removed a required file, acritical system file, or HDD sector content. Then, at block 706, theprimary OS, which is now corrupted, “limps along” while the usercontinues to attempt to interact with the IHS, whether or not theprimary OS is responsive to those attempts.

At block 710 and in response to block 705, the OS hypervisor detects thefile change or storage device read/write error. Then, at block 711, theOS hypervisor notifies the service OS of the change or error. In somecases, the change may be legitimate, yet the service OS may inspect itin order to make such a determination.

At block 714, the service OS determines that the primary OS has beensignificantly altered. For example, the service OS may have a list ofproblem codes that, once detected, indicate that the alternations havebeen significant enough to trigger corrective action. In variousimplementations, different groups of problem codes may trigger differentactions. So, at block 715, the service OS inspects and remediates theprimary OS, boot media, and control; and restores any required files (inmore extreme scenarios), as shown in FIGS. 8 and 9 below. Particularly,at block 712 the service OS may access APIs provided by the OShypervisor that enable read/write access by the service OS to theprimary OS's file system and/or media.

At block 707, the primary OS is inspected and repaired by the serviceOS. And, at block 708, the repaired primary OS is put into normaloperation by a user. Conversely, at block 716, the service OS determineswhether the primary OS should be rebooted, for example, based on rulesthat indicate a reboot for a subset of problem codes on the code list.At block 717, if a reboot is deemed necessary by the service OS, thenthe service OS requests a restart of the primary OS to the OShypervisor. At block 713, the OS hypervisor restarts the primary OS,which takes place at block 709.

FIG. 8 is a diagram of an example of a system for migrating data out ofa hard disk partition into RAM. In this implementation, HDD 218 of FIG.2 is shown as hybrid storage drive 218A having magnetic partition 801Aand Solid State Drive (SSD) partition 804A housed within a singlestorage device. Primary OS 802A and primary data files 803A reside inmagnetic partition 801A. Meanwhile, alternate or service OS 805A andbackup files 806A reside in SSD partition 804A. Memory 206 of FIG. 2 isimplemented as Dynamic RAM (DRAM) 206, and it is configured to store abackup of SSD partition 804A in area 807 prior to a replacement or hotswapping operation.

In some cases, upon detection of a failure of HDD 218A by OS hypervisor,primary OS, and/or service OS, the user may need to replace potentiallydefective HDD 218A with a new HDD 218B. After HDD 218A is removed fromthe IHS and new HDD 218B replaces it, the contents of area 807, which inare shown in FIG. 9 as service OS 805B and backup files 806B (and whichare copies of elements 805A and 806A), are subject to restore operation900 to move them out of DRAM area 807 and into SSD partition 804B of newHDD 218B. Magnetic storage portion 801B may be used to install a cleancopy of primary OS 802A and/or primary data files 803A.

It should be understood that various operations described herein may beimplemented in software executed by logic or processing circuitry,hardware, or a combination thereof. The order in which each operation ofa given method is performed may be changed, and various operations maybe added, reordered, combined, omitted, modified, etc. It is intendedthat the invention(s) described herein embrace all such modificationsand changes and, accordingly, the above description should be regardedin an illustrative rather than a restrictive sense.

Although the invention(s) is/are described herein with reference tospecific embodiments, various modifications and changes can be madewithout departing from the scope of the present invention(s), as setforth in the claims below. Accordingly, the specification and figuresare to be regarded in an illustrative rather than a restrictive sense,and all such modifications are intended to be included within the scopeof the present invention(s). Any benefits, advantages, or solutions toproblems that are described herein with regard to specific embodimentsare not intended to be construed as a critical, required, or essentialfeature or element of any or all the claims.

Unless stated otherwise, terms such as “first” and “second” are used toarbitrarily distinguish between the elements such terms describe. Thus,these terms are not necessarily intended to indicate temporal or otherprioritization of such elements. The terms “coupled” or “operablycoupled” are defined as connected, although not necessarily directly,and not necessarily mechanically. The terms “a” and “an” are defined asone or more unless stated otherwise. The terms “comprise” (and any formof comprise, such as “comprises” and “comprising”), “have” (and any formof have, such as “has” and “having”), “include” (and any form ofinclude, such as “includes” and “including”) and “contain” (and any formof contain, such as “contains” and “containing”) are open-ended linkingverbs. As a result, a system, device, or apparatus that “comprises,”“has,” “includes” or “contains” one or more elements possesses those oneor more elements but is not limited to possessing only those one or moreelements. Similarly, a method or process that “comprises,” “has,”“includes” or “contains” one or more operations possesses those one ormore operations but is not limited to possessing only those one or moreoperations.

The invention claimed is:
 1. An Information Handling System (IHS), comprising: a processor; and a memory coupled to the processor, the memory having program instructions stored thereon that, upon execution by the processor, cause the IHS to: provide an Operating System (OS) hypervisor configured to manage a primary OS environment and a service OS environment concurrently, wherein the primary and service OS environments are distinct from each other; allow the service OS, via the OS hypervisor, to monitor a state of the primary OS while forbidding the primary OS from monitoring a state of the service OS; detect, by the OS hypervisor, that a primary OS event has taken place; and notify the service OS, by the OS hypervisor, of the primary OS event.
 2. The IHS of claim 1, wherein the service OS includes one or more diagnostic tools.
 3. The IHS of claim 1, wherein monitoring the state of the primary OS includes accessing the state using an Application Programming Interface (API) provided by primary OS via the OS hypervisor to enable one-way access to the primary OS by the service OS.
 4. The IHS of claim 3, wherein the API includes a disk, file, or memory access API.
 5. The IHS of claim 1, wherein the program instructions upon execution by the processor, further cause the IHS to allow the service OS to suspend, stop, or restart the primary OS via the OS hypervisor.
 6. The IHS of claim 1, wherein the program instructions, upon execution by the processor, further cause the IHS to: determine, by the service OS via the OS hypervisor, that the primary OS event meets a threshold; and take corrective action, by the service OS via the OS hypervisor, upon the primary OS.
 7. The IHS of claim 6, wherein the corrective action includes restoring a file affected by the primary OS event.
 8. The IHS of claim 6, wherein the corrective action includes a reboot of the primary OS.
 9. The IHS of claim 6, wherein the program instructions, upon execution by the processor, further cause the IRS to backup a partition where the service OS resides into a Random Access Memory (RAM) prior to the determination.
 10. The IHS of claim 9, wherein the partition includes a solid-state portion of a hybrid Hard Disk Drive (HDD), and wherein the primary event includes an HDD failure.
 11. The IHS of claim 9, wherein the program instructions, upon execution by the processor, further cause the IRS to restore the backup from the RAM to a replacement HDD in connection with a hot-swapping operation.
 12. A computer-implemented method, comprising: providing an Operating System (OS) hypervisor configured to host a primary OS and a service OS, wherein the primary and service OS are distinct from each other; allowing the service OS, using one or more one-way Application Programming Interfaces (APIs) provided via the OS hypervisor, to monitor the primary OS while the primary OS is being executed; detecting, by the OS hypervisor, that a primary OS event has taken place; and notifying the service OS, by the OS hypervisor, of the primary OS event.
 13. The computer-implemented method of claim 12, further comprising allowing the service OS to suspend, stop, or restart the primary OS via the OS hypervisor.
 14. The computer-implemented method of claim 12, further comprising: in response to the notification, taking corrective action, by the service OS via the OS hypervisor, upon the primary OS.
 15. The computer-implemented method of claim 14, wherein the corrective action includes restoring a file affected by the primary OS event or rebooting the primary OS.
 16. The computer-implemented method of claim 14, wherein the corrective action includes restoring a backup of a partition where the service OS resides from a Random Access Memory (RAM) to a replacement HDD.
 17. A storage device having program instructions stored thereon that, upon execution by an Information Handling System (IHS), cause the IHS to: provide an Operating System (OS) hypervisor configured to host concurrent execution of a primary OS and a service OS, wherein the primary and service OS are distinct from each other; and allow the service OS, using one or more one-way Application Programming Interfaces (APIs) provided via the OS hypervisor, to monitor the primary OS while the primary OS is being executed; detect, by the OS hypervisor, that a primary OS event has taken place; and notify the service OS, by the OS hypervisor, of the primary OS event.
 18. The storage device of claim 17, wherein the program instructions, upon execution by the processor, further cause the IHS to: in response to the notification, take corrective action, by the service OS via the OS hypervisor, upon the primary OS.
 19. The storage device of claim 18, wherein the corrective action includes restoring a file affected by the primary OS event, rebooting the primary OS, or restoring an HDD partition from a Random Access Memory (RAM) to a replacement HDD. 